Synchronizing an application on a companion device

ABSTRACT

A media server machine may be configured to provide media content within a datastream. This datastream may be provided to a media device that is configured to present the media content on a display. Also, this datastream may contemporaneously contain an “app-sync indicator” for the media content. The app-sync indicator is a data structure that signals the media device to launch an application on a companion device. By providing the app-sync indicator contemporaneously with the media content in the datastream, the launching of the application on the companion device may be synchronized with the media content. The app-sync indicator may specify the application to be launched. Also, the app-sync indicator may specify supplemental content to be presented by the launched application on the companion device.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.13/905,779, filed May 30, 2013, now U.S. Pat. No. 9,143,565, issued Sep.22, 2015.

TECHNICAL FIELD

The subject matter disclosed herein generally relates to the processingof data. Specifically, the present disclosure addresses systems andmethods to synchronize an application on a companion device.

BACKGROUND

Media content may be transmitted over a network (e.g., a cabletelevision network, the Internet, or a satellite television network) andreceived by a media device that is communicatively coupled (e.g., by awired or wireless connection) to a display. For example, media contentin the example form of a television show or sports event may bemultiplexed into a transport stream and broadcast via the network to oneor more media devices within users' homes. Examples of such mediadevices include integrated receiver-decoders (IRDs), personal videorecorders (PVRs), and other set-top boxes (STBs) that may be connectedto a display (e.g., a television screen, a video monitor, or othersuitable display device). Such media devices may be configured topresent (e.g., display) the media content on the display.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings.

FIG. 1 is a network diagram illustrating a network environment suitablefor synchronizing an application on a companion device, according tosome example embodiments.

FIG. 2 is a block diagram illustrating components of a media servermachine suitable for synchronizing the application on the companiondevice, according to some example embodiments.

FIG. 3 is a block diagram illustrating components of a media devicesuitable for synchronizing the application on the companion device,according to some example embodiments.

FIG. 4 is a block diagram illustrating components of the companiondevice, according to some example embodiments.

FIG. 5 is a flowchart illustrating data flows within the networkenvironment, according to some example embodiments.

FIG. 6 is a flowchart illustrating operations of the media servermachine in performing a method of synchronizing an application on thecompanion device, according to some example embodiments.

FIG. 7-9 are flowcharts illustrating operations of the media device inperforming a method of synchronizing the application on the companiondevice, according some example embodiments.

FIG. 10 is a flowchart illustrating operations of the companion devicein performing a method of synchronizing the application, according tosome example embodiments.

FIG. 11 is a block diagram illustrating relationships among mediacontent, app-sync indicators, and supplemental content that is pertinentto the media content, according to some example embodiments.

FIG. 12 is a block diagram illustrating components of a machine,according to some example embodiments, able to read instructions from amachine-readable medium and perform any one or more of the methodologiesdiscussed herein.

DETAILED DESCRIPTION

Example methods and systems are directed to synchronization of anapplication on a companion device. Examples merely typify possiblevariations. Unless explicitly stated otherwise, components and functionsare optional and may be combined or subdivided, and operations may varyin sequence or be combined or subdivided. In the following description,for purposes of explanation, numerous specific details are set forth toprovide a thorough understanding of example embodiments. It will beevident to one skilled in the art, however, that the present subjectmatter may be practiced without these specific details.

A media server machine (e.g., a computer system or other processingdevice) may be configured (e.g., by one or more software modules) toprovide media content within a datastream. This datastream may beprovided to a media device that is configured to present the mediacontent on a display (e.g., a primary display). Also, this datastreammay contain (e.g., contemporaneously) an “app-sync indicator” for themedia content (e.g., an app-sync indicator that corresponds to the mediacontent). The app-sync indicator is a data structure that signals themedia device to launch an application on a companion device (e.g., atablet computer or smart phone operable present additional content on asecondary display). By providing the app-sync indicator with the mediacontent (e.g., contemporaneously) in the datastream, the launching ofthe application on the companion device may be synchronized with themedia content.

For example, the datastream may be a multiplexed transport stream withinwhich the media content is contained within a program stream, and theapp-sync indicator may take the form of a table (e.g., an applicationinformation table (AIT) or other table) that is also multiplexed (e.g.,as carousel data) into the same transport stream, same program stream,or both. This table, after being received by the media device, may causethe media device to generate and send a launch instruction to thecompanion device. The launch instruction, after being received by thecompanion device, may cause the companion device to launch anapplication (e.g., begin executing the application) while the mediacontent is being presented on the display by the media device.

The app-sync indicator may specify the application (e.g., a mobile app)to be launched. Also, the app-sync indicator may specify supplementalcontent to be presented by the launched application. For example, theapp-sync indicator may specify that a web browser be launched with aparticular uniform resource identifier (URI) (e.g., a uniform resourcelocator (URL)) as input, so that the web browser presents supplementalcontent identified by that particular URI. As another example, supposingthe media content is a sports event (e.g., a baseball game in which aparticular team is playing), the app-sync indicator may specify that amobile app (e.g., corresponding to the particular team) be launched topresent supplemental content that corresponds to the sports event (e.g.,information about individual players on that particular baseball team).As a further example, where the media content is a sports event, (e.g.,a football game), the app-sync indicator may specify that a web browseror app be launched to present supplemental content in the form ofstreaming video that depicts an alternate camera angle (e.g., differentfrom a primary camera angle depicted in the media content). Accordingly,the supplemental content may be pertinent to the media content, maycorrespond to the media content, and may reference the media content,while yet being separate, distinct, independent, and different from themedia content. Additional details of various example embodiments arediscussed below.

FIG. 1 is a network diagram illustrating a network environment 100,according to some example embodiments. The network environment 100includes a media server machine 110, a database 115, a web servermachine 120, a media device 140, and companion devices 130 and 150. Themedia server machine 110 and the media device 140 may be communicativelycoupled to each other via a network 190 (e.g., a cable televisionnetwork, satellite television network, the Internet, a cellulartelephone network, any other network capable of communicating digitaldata, or any suitable combination of networks). The companion devices130 and 150 may each be communicatively coupled to the media servermachine 110, the web server machine 120, or both, by another network 192(e.g., a telephone network, a cellular network, a cable Internetnetwork, a local area network (LAN), a wide area network (WAN), or anysuitable combination thereof). In addition, one or both of the companiondevices 130 and 150 may be communicatively coupled to the media device140 (e.g., by an infrared (IR) or wireless peer-to-peer LAN, or othersuitable connection).

As noted in FIG. 1, the media server machine 110 may be or include acable television server, satellite television service, or both. Thedatabase 115 may store media content (e.g., movies, television shows,sports events, educational programs, newscasts, or portions thereof,such as individual scenes, clips, cuts, or frames of such mediacontent), applications (e.g., mobile app) that may correspond to mediacontent, supplemental content for media content, or any suitablecombination thereof. The media server machine 110, with or without thedatabase 115 may form all or part of a network-based media system 105(e.g., a cloud-based media “head end” system). In some exampleembodiments, the network-based media system also includes the web servermachine 120.

The web server machine 120 may be or include an Internet streaming videoserver (e.g., configured to provide supplemental content in the form ofon-demand video, such as, alternate camera angles that complement mediacontent). The media device 140 may be or include an IRD or other STBsuitable for presenting media content on the display 142 (e.g., atelevision, display screen, or other video-capable monitor), which maybe communicatively coupled (e.g., by a wired or wireless connection) tothe media device 140. In some example embodiments, the media device 140is or includes a home media server computer. One or both of thecompanion devices 130 and 150 may be or include a tablet computer, asmart phone, a laptop computer, an e-book reader, or any suitablecombination thereof. The media server machine 110, the database 115, theweb server machine 120, the media device 140, and the companion devices130 and 150 may each be implemented in a computer system, in whole or inpart, as described below with respect to FIG. 12.

Also shown in FIG. 1 are users 132 and 152. One or both of the users 132and 152 may be a human user (e.g., a human being), a machine user (e.g.,a computer configured by a software program to interact with thecompanion device 130), or any suitable combination thereof (e.g., ahuman assisted by a machine or a machine supervised by a human). Theuser 132 is not part of the network environment 100, but is associatedwith the companion device 130 and may be a user of the companion device130. For example, the companion device 130 may be a desktop computer, avehicle computer, a tablet computer, a navigational device, a portablemedia device, or a smart phone belonging to the user 132. Likewise, theuser 152 is not part of the network environment 100, but is associatedwith the companion device 150. As an example, the companion device 150may be a desktop computer, a vehicle computer, a tablet computer, anavigational device, a portable media device, or a smart phone belongingto the user 152.

Any of the machines, databases, or devices shown in FIG. 1 may beimplemented in a general-purpose computer modified (e.g., configured orprogrammed) by software to be a special-purpose computer to perform oneor more of the functions described herein for that machine, database, ordevice. For example, a computer system able to implement any one or moreof the methodologies described herein is discussed below with respect toFIG. 12. As used herein, a “database” is a data storage resource and maystore data structured as a text file, a table, a spreadsheet, arelational database (e.g., an object-relational database), a triplestore, a hierarchical data store, or any suitable combination thereof.Moreover, any two or more of the machines, databases, or devicesillustrated in FIG. 1 may be combined into a single machine, and thefunctions described herein for any single machine, database, or devicemay be subdivided among multiple machines, databases, or devices.

The network 190 and the network 192 each may be a network that enablescommunication between or among machines, databases, and devices (e.g.,the media server machine 110 and the companion device 130). Accordingly,one or both of the network 190 and 192 may be a wired network, awireless network (e.g., a mobile or cellular network), or any suitablecombination thereof. One or both of the networks 190 and 192 may includeone or more portions that constitute a private network, a public network(e.g., the Internet), or any suitable combination thereof. In someexample embodiments, the networks 190 and 192 are combined into a singlenetwork. In certain example embodiments, the companion devices 130 and150 are connected to the web server machine 120 by separate networks.

FIG. 2 is a block diagram illustrating components of the media servermachine 110, according to some example embodiments. The media servermachine 110 is shown as including a generator module 210, a provisionmodule 220, and a server module 230, all configured to communicate witheach other (e.g., via a bus, shared memory, or a switch). Any one ormore of the modules described herein may be implemented using hardware(e.g., a processor of a machine) or a combination of hardware andsoftware. For example, any module described herein may configure aprocessor to perform the operations described herein for that module.Moreover, any two or more of these modules may be combined into a singlemodule, and the functions described herein for a single module may besubdivided among multiple modules. Furthermore, according to variousexample embodiments, modules described herein as being implementedwithin a single machine, database, or device may be distributed acrossmultiple machines, databases, or devices.

The generator module 210 may be or include a multiplexer module (e.g.,configured to generate a datastream by multiplexing data such as variousmedia content, one or more applications executable by the companionmodule 130, and one or more app-sync indicators). The provision module220 may be or include a distributor module (e.g., configured to providethe datastream by distributing the datastream to various media devices,including the media device 140).

In some example embodiments, the media server machine 110 includes aserver module 230 (e.g., in the form of an application generator, amodule distributor, or both). The server module 230 may generate one ormore software modules, and store them before providing one or more ofthem to a device (e.g., media device 140 or companion device 130). Inthe example shown in FIG. 2, the server module 230 is storing asynchronization module 232, as well as a companion module 234. Thesynchronization module 232 may be usable to configure one or more mediadevices (e.g., media device 140). The companion module 234 may be usableto configure one or more companion devices (e.g., companion device 130).The server module 230 may generate, store, and provide one or both ofthe synchronization module 232 and the companion module 234. Forexample, the synchronization module 232 may be provided to the mediadevice 140, and the companion module 234 may be provided to one or bothof the companion devices 130 and 150.

Certain example embodiments of the media device 140 support an automaticdevice discovery feature (e.g., for automatically detecting one or morecompanion devices). When a new person bearing new companion deviceenters a room during an activity that involves media content beingpresented on the display 142 (e.g., during gameplay of the game), thenew person may be invited (e.g., automatically or manually) to join theexisting activity (e.g., the game), based on the new companion devicebeing automatically detected by the media device 140. The joining of theperson to the activity may also be automatic. Alternatively,non-automatic joining of the person may be configured, for example, byimplementing an authorization step such that an authorization to add thenew person is obtained (e.g., by the media device 140, from the mediaserver 110, the database 115, or the web server machine 120) prior tojoining the new person to the activity. This feature may be useful in adynamic local audience multi-player scenario (e.g., during mediaevents). This feature may be implemented, wholly or partially, using theDiscovery And Launch (DIAL) protocol by Netflix, Inc., using anotherprotocol, or using any suitable combination of protocols.

According to some example embodiments, the synchronization module 232,the companion module 234, or both, may be or include a DIAL server(e.g., a server application that supports the DIAL protocol by Netflix,Inc.), a DIAL client (e.g., a client application that supports the DIALprotocol), or both. The synchronization module 232, the companion module234, or both, may also be or include a Representational State Transfer(REST) server, REST client, or both.

In some example embodiments, the server module 230 is or includes anevent signaling generator. In such example embodiments, the servermodule 230 is configured to generate one or more synchronization signals(e.g., metadata similar to an AIT) that are usable by the media device140 to initiate one or more additional actions (e.g., beyond sendinglaunch instructions) that cause the companion device 130 to perform oneor more further actions. Such synchronization signals may be provided tothe media device 140 in the datastream (e.g., contemporaneously withmedia content and a corresponding app-sync indicator). This may have theeffect of causing the companion device 130 to perform such furtheractions at the appropriate time in synchronization with the mediacontent.

In certain example embodiments, the server module 230 is configured togenerate and distribute one or more upgrades for the media device 140,the companion device 130, or both (e.g., upgrades to the synchronizationmodule 232, the companion module 234, an operating system, middleware,or any suitable combination thereof).

FIG. 3 is a block diagram illustrating components of the media device140, according to some example embodiments. The media device 140 isshown as including a reception module 310, a presentation module 320, adetection module 330, and the synchronization module 232 (e.g.,generated and provided by the media server machine 110), all configuredto communicate with each other (e.g., via a bus, shared memory, or aswitch). As noted above, any one or more of these modules may beimplemented using hardware (e.g., a processor of a machine), and anymodule described herein may configure a processor to perform theoperations described herein for that module.

The reception module 310 is configured to receive the datastreamprovided by the media server machine 110 (e.g., from its provisionmodule 220). The presentation module 320 is be configured to extract themedia content from the datastream and present the media content on thedisplay 142. The detection module 330 is configured to detect one ormore companion devices (e.g., companion device 130) being moved (e.g.,by the user 132) to within physical proximity of the media device 140,for example, being moved within a threshold distance of the media device140 (e.g., within IR signal range, within wireless networking range, orwithin a predetermined distance as determined by geolocation techniques,such as by use of global positioning system (GPS) data) and establishone or more communication links with such detected companion devices. Insome example embodiments, the server module 230 of the media servermachine 110 generates the detection module 330, provides the detectionmodule 330 to the media device 140, or both.

The synchronization module 232 may be or include a DIAL client (e.g.,configured to launch one or more applications on the companion device130, which may implement a DIAL server), and the synchronization module232 may be configured to generate and send a launch instruction to oneor more companion devices (e.g., companion devices 130 and 150). Such alaunch instruction may be generated, sent, or both, based on an app-syncindicator provided (e.g., contemporaneously) with media content within adatastream from the media server machine 110. For example, the launchinstruction may be generated and sent in response to the fact that theapp-sync indicator is provided (e.g., contemporaneously) with the mediacontent. The launch instruction may specify an application to belaunched, supplemental content to be presented by the application, orboth. In some example embodiments, the synchronization module 232 formsall or part of an application that is stored by the media device 140 andlaunched (e.g., executed) by the media device 140 (e.g., in response tothe presence of the app-sync indicator in the datastream, in response todetection of one or more companion devices, in response to accessing thedatastream, in response to user input, or any suitable combinationthereof).

FIG. 4 is a block diagram illustrating components of the companiondevice 130, according to some example embodiments. The companion device150 may be similarly configured. The companion device 130 is shown asincluding an access module 410, a presentation module 420, a detectionmodule 430, an application 440 (e.g., a browser or a mobile app), ascreen 450 (e.g., a touchscreen or other display screen), and thecompanion module 234 (e.g., generated provided by the media servermachine 110), all configured to communicate with each other (e.g., via abus, shared memory, or a switch). As noted above, any one or more ofthese modules may be implemented using hardware (e.g., a processor of amachine), and any module described herein may configure a processor toperform the operations described herein for that module.

The access module 410 is configured to receive a launch instruction sentfrom the media device 140. The access module 410 may be furtherconfigured to access (e.g., receive, retrieve, or otherwise obtain)supplemental content from the web server machine 120. The presentationmodule 420 is configured to present the supplemental content on thescreen 450. The detection module 430 is configured to detect one or moremedia devices (e.g., media device 140) coming within physical proximityof the companion device 130, for example, coming within a thresholddistance of the companion device 130 (e.g., within IR signal range,within wireless networking range, or within a predetermined distance asdetermined by geolocation techniques, such as by use of GPS data) andestablish one or more communication links with such detected mediadevices.

The companion module 234 may be or include a DIAL server (e.g.,configured to launch one or more applications on the companion device130 at the request of a DIAL client), and the companion module 234 maybe configured to launch the application 440, which may be stored at thecompanion device 130 (e.g., after being downloaded to the companiondevice 130 from the media server machine 110, from the media device 140,from the web server machine 120, or any suitable combination thereof).The launching of the application 440 may be in response to the launchinstruction received by the access module 410. The launch instructionmay specify the application 440 to be launched, and the launchinstruction may specify (e.g., identify, indicate, or locate)supplemental content to be accessed by the access module 410 andpresented by the application. In some example embodiments, the companionmodule 234 forms all or part of an application that is stored by thecompanion device 130 and launched (e.g., executed) by the companiondevice 130 (e.g., in response detection of one or more media devices, inresponse to user input, or both).

The application 440 may be or include a browser, a mobile app, or othersoftware suitable for presenting supplemental content. In some exampleembodiments, the companion device 130 is adequate to execute theapplication 440, while the media device 140 is inadequate to execute theapplication 440. For example, the media device 140 may lack the hardwareresources (e.g., processor speed or memory) to execute the application440.

The screen 450 may be a touchscreen (e.g., a touch-sensitive displayscreen) of the companion device 130. Accordingly, while the media device140 may present media content on the display 142 (e.g., a primarydisplay or primary screen), the companion device 130 may presentsupplemental content on the screen 450 (e.g., secondary display orsecondary screen).

FIG. 5 is a flowchart illustrating data flows within the networkenvironment 100 during performance of a method 500 for synchronizing theapplication 440 on the companion device 130, according to some exampleembodiments. In operation 501, the generator module 210 of the mediaserver machine 110 obtains media content (e.g., accesses, receives, orretrieves media content from an upstream media source, such as atelevision station, a satellite, or other provider of media content). Inoperation 510, the generator module 210 of the media server machine 110generates an app-sync indicator for inclusion (e.g., contemporaneousinclusion, so that the presentation time of the app-sync indicator fallswithin the presentation times of the media content) with the mediacontent in a datastream. In operation 520, the generator module 210generates the datastream that includes (e.g., contemporaneously) themedia content and the app-sync indicator for the media content. Forexample, the generator module 210 may generate a datastream bymultiplexing the media content with the app-sync indicator (e.g., in theform of a data table) into the resulting datastream.

In operation 530, the provision module 220 of the media server machine110 provides the datastream to the media device 140 (e.g., via thenetwork 190). The datastream may be provided via any one or more datacommunication technologies (e.g., cable television network, satellitetelevision network, a cellular telephone network. Internet protocoltelevision (IPV), hypertext transfer protocol live streaming (HLS), overthe top (OTT) streaming, or any suitable combination thereof). Operation530 may include providing the app-sync indicator (e.g.,contemporaneously) with the media content to the media device 140. Forexample, the app-sync indicator may be provided with its presentationtime (e.g., a time at which the media device 140 takes action on theapp-sync indicator) falling within the presentation times of the mediacontent (e.g., a range of times at which the media device 140 presentsthe media content, such as, the duration of a clip, scene, or program).As noted above, the media device 140 may be configured to present themedia content on the display 142, to detect the companion device 130,and to send a launch instruction to the companion device 130 based onthe app-sync indicator. As also noted above, the companion device 130may be configured to launch the application 440 in response to thelaunch instruction sent from the media device 140.

In operation 505, the detection module 330 of the media device 140detects the companion device 130 (e.g., detects the presence of thecompanion device 130 within IR range, wireless networking range, or apredetermined threshold distance of the media device 140). The mediadevice 140 may thereafter establish a communication link with thedetected companion device 130. In some example embodiments, prior tooperation 505, the media server machine 110 provides the detectionmodule 330 to the media device 140.

In operation 531, the reception module 310 of the media device 140accesses (e.g., receives, reads, or retrieves) the datastream providedby the media server machine 110. Hence, the reception module 310 mayaccess (e.g., receive) the media content (e.g., contemporaneously) withthe app-sync indicator. In operation 535, the presentation module 320 ofthe media device 140 presents the media content on the display 142. Inoperation 540, the synchronization module 232 on the media device 140sends a launch instruction to the companion device 130 (e.g., via IRsignals or a wireless peer-to-peer network). The launch instruction maybe usable by the companion device 130 to launch the application 440.

In operation 541, the access module 410 of the companion device 130receives the launch instruction sent from the media device 140. Thelaunch instruction may reference the application 440 (e.g., a browser).In operation 550, the companion module 234 on the companion device 130,in response to the launch instruction, launches the application 440.Since the time between operations 535 and 550 may be perceived by theuser 132 as being subjectively short (e.g., under one second), thelaunching of the application 440 may be perceived by the user 132 asbeing synchronized with the presentation of the media content. Theapplication 440 may cause the access module 410 of the companion device130 to access supplemental content from the web server machine 120, andthe application 440 may cause presentation module 420 of the companiondevice 130 to present the accessed supplemental content on the screen450 of the companion device.

FIG. 6 is a flowchart illustrating operations of the media servermachine 110 in performing a method 600 of synchronizing the application440 on the companion device 130, according to some example embodiments.Operations in the method 600 may be performed using modules describedabove with respect to FIG. 2. As shown in FIG. 6, the method 600includes operations 501, 510, 520, and 530, and may include one or moreof operations 601, 602, 603, 604, 610, 611, 620, 630, and 640.

In operation 601, the server module 230 generates the synchronizationmodule 232 (e.g., for the media device 140). For example, the servermodule 230 may assemble the synchronization module 232 as a data packageof various software subcomponents (e.g., a DIAL client and a list oftrusted companion devices, such as the companion devices 130 and 150).Operation 601 may include creating the synchronization module 232 orupdating (e.g., modifying) the synchronization module 232.

In operation 602, the server module 230 provides the synchronizationmodule 232 to the media device 140 (e.g., via the network 190). Inresponse, the media device 140 may be configured, at least in part, bythe synchronization module 232.

In operation 603, the server module 230 generates the companion module234 (e.g., for the companion devices 130 and 150). For example, theserver module 230 may assemble the companion module 234 as a datapackage of various software subcomponents (e.g., a DIAL server and alist of trusted web server machines, such as the web server machine120). Operation 603 may include creating the companion module 234 orupdating (e.g., modifying) the companion module 234).

In operation 604, the server module 230 provides the companion module234 to the media device 140 (e.g., via the network 190, for subsequentprovision by the media device 140 to the companion device 130) or to thecompanion device 130 (e.g., via the network 192). In response toreceiving the companion module 234, the synchronization module 232 ofmedia device 140 may provide (e.g., relay) the companion module 234 tothe companion device 130. In response to receiving the companion module234, the companion device 130 may be configured, at least in part, bythe companion module 234.

In the method 600, operations 501, 510, 520, and 530 may each beperformed in a manner similar to that described above with respect toFIG. 5. One or more of operations 610 and 611 may be performed as part(e.g., a precursor task, a subroutine, or a portion) of operation 510,in which the generator module 210 of the media server machine 110generates the app-sync indicator.

In operation 610, the generator module 210 embeds a reference (e.g., anidentifier or a pointer) to the supplemental content for the mediacontent into the app-sync indicator. For example, the embedded referencemay be or include a URI (e.g., URL) that identifies (e.g., names,locates, or both) the supplemental content, which corresponds to themedia content. This reference may be extracted by the media device 140and included in the launch instruction sent to the companion device 130,which may launch the application 440 with the reference as an input tothe application 440.

In operation 611, the generator module 210 embeds an identifier of theapplication 440 into the app-sync indicator (e.g., a name of theapplication 440, with or without an authentication code). In situationswhere multiple applications (e.g., application 440) are available forbeing synchronously launched with the media content, embedding theidentifier of the application 440 into the app-sync indicator enablesthe media device 140 to send one or more launch instructions based onthe app-sync indicator identifying the application 440. For example, themedia device 140 may send a launch instruction that specifies whichapplication (e.g., application 440) is to be synchronously launched withthe media content. Accordingly, the companion device 130 may launch theapplication 440 based on the launch instruction identifying theapplication 440.

Operation 620 may be performed as part of operation 520, in which thegenerator module 210 of the media server machine 110 generates thedatastream. In operation 620, the generator module 210 embeds theapplication 440 into the datastream. For example, the application 440may be stored by the database 115, and the generator module 210 mayaccess the application 440 from the database 115 and multiplex theapplication 440 into the datastream so that the application 440 may beprovided within the datastream to the media device 140 for subsequentprovision to the companion device 130. Although the app-sync indicatorand the media content may be provided contemporaneously together (e.g.,with each other, so that the presentation time of the app-sync indicatorfalls within the presentation times of the media content) within thedatastream, the application 440 may be provided prior to the mediacontent and the app-sync indicator within the datastream. In suchsituations, the synchronization module 232 of the media device 140 mayprovide (e.g., relay) the application 440 to the companion device 130for storage thereon, so that the application 440 may be launched at theappropriate time (e.g., in sync with the media content being presentedon the display 142 by the media device 140). As another example, thesynchronization module 232 may provide a URL from which the application440 can be obtained by the companion device 130.

According to some example embodiments, the network 190 may be optimizedfor broadcast of media content, while the network 192 may be optimizedfor interactive selection and presentation of supplemental content.Operation 630 may be performed as part of operation 530, in which theprovision module 220 of the media server machine 110 provides thedatastream. In operation 630, the provision module 220 provides thedatastream via the network 190 (e.g., a first network), which may becontrasted with the network 192 (e.g., a second network). Operation 640may be performed with or after operation 530. In operation 640, theprovision module 220 provides the supplemental content via the network192 (e.g., the second network). For example, the supplemental contentmay be stored by the database 115, the media server machine 110, the webserver machine 120, or any suitable combination thereof, and thesupplemental content may be provided by the provision module 220 to thecompanion device 130 (e.g., in response to the launching of theapplication 440 with a reference to the supplemental content as an inputparameter). This providing of the supplemental content may be relayedthrough the web server machine 120.

FIG. 7-9 are flowcharts illustrating operations of the media device 140in performing a method 700 of synchronizing the application 440 on thecompanion device 130, according some example embodiments. Operations inthe method 700 may be performed using modules described above withrespect to FIG. 3. As shown in FIG. 7, the method 700 includesoperations 531, 535, and 540 and may include one or more of operations731, 732, 733, 734, 735, 736, 737, and 738.

Operation 731 may be performed as part of operation 531, in which thereception module 310 of the media device 140 receives the datastreamprovided by the media server machine 110. In operation 731, thereception module 310 receives the application 440 embedded in thedatastream. This may enable the synchronization module 232 of the mediadevice 140 to provide (e.g., relay) the application 440 to the companiondevice 130 (e.g., for storage thereon, in preparation for launching theapplication 440 in sync with the presentation of the media content bythe presentation module 320 of the media device 140 on the display 142).

In operation 732, the synchronization module 232 extracts an identifier(e.g., an application name, with or without an authentication code) ofthe application 440 from the app-sync indicator. As noted above, theidentifier of the application 440 may be embedded in the app-syncindicator, and may identify the application 440 among multipleapplications. Operation 733 may be performed before, during, or afteroperation 531. In operation 733, the synchronization module 232determines that the application 440 is on a trusted list (e.g., a listof trusted applications, among which is the application 440), which mayhave the effect of providing a degree of security checking that onlytrusted applications are launched on the companion device 130. Accordingto various example embodiments, this determination may be performedbased on the extracted identifier from operation 732, performed inresponse to the application being received in operation 731, or both.The trusted list may be included (e.g., stored) in the synchronizationmodule 232 (e.g., as generated by the server module 230 of the mediaserver machine 110) or provided to the synchronization module 232 (e.g.,as an update) by the media server machine 110, by the database 115, orby the web server machine 120 (e.g., via secure sockets layer (SSL)communication).

In operation 734, the synchronization module 232 provides theapplication 440 to the companion device 130 for storage thereon,execution thereon, or both. In some example embodiments, the application440 is provided via a communication link established between the mediadevice 140 and the companion device 130 (e.g., an IR or wirelessconnection). In situations where the application 440 is already storedon the companion device 130, operation 734 may be omitted. Similarly,operation 734 may be omitted in situations where the companion device130 is configured to obtain (retrieve, fetch, or access) the application440 based on the URL provided by the synchronization module 232.

In operation 735, the synchronization module 232 extracts the referenceto the supplemental content from the app-sync indicator (e.g., thereference that was embedded in operation 610). For example, thesynchronization module 232 may extract a URI (e.g., URL) that identifiesthe supplemental content to be presented by the application 440 launchedwhile the media content is being presented on the display 142. Exampleembodiments that include operation 735 may also include operation 736.Operation 736, the synchronization module 232 determines that thereference (e.g., the URL) is on a trusted list (e.g., a list of trustedreferences to supplemental content, such as URLs served by the webserver machine 120), which may have the effect of providing a degree ofsecurity checking that only trusted references to supplemental contentare used. This determination may be performed based on the extractedreference from operation 735, performed in response to the app-syncindicator being received in operation 531, or both. The trusted list maybe included (e.g., stored) in the synchronization module 232 (e.g., asgenerated by the server module 230 of the media server machine 110) orprovided to the synchronization module 232 (e.g., as an update) by themedia server machine 110, by the database 115, or by the web servermachine 120 (e.g., via SSL communication).

In operation 737, as shown in FIG. 7-8, the synchronization module 232causes the media device 140 to present a suggestion that the companiondevice 130 (e.g., specifically as the companion device 130, orgenerically as one of multiple available companion devices) present thesupplemental content (e.g., referenced by the app-sync indicator). Forexample, as shown in FIG. 8, operation 737 may include operation 830, inwhich the synchronization module 232 presents a suggestion on thedisplay 142 (e.g., by causing the presentation module 320 of the mediadevice 14 o to present the suggestion on the display 142). As anotherexample, shown in FIG. 8, operation 737 may include operation 831, inwhich the synchronization module 232 causes the companion device 130(e.g., via its presentation module 420, its companion module 234, orboth) to present the suggestion on its screen 450 (e.g., by sending aprompt to the companion module 234 of the companion device 130).

According to various example embodiments, the suggestion may take theform of a single icon (e.g., a single green button that identifies abutton or key on a remote control that is configured to fully orpartially control the media device 140 by selecting media content forpresentation on the display 142). Such a single icon may indicateavailability of the supplemental content for presentation, identify abutton or key (e.g., on a remote control, on the companion device 130,or both) that is operable to submit an acceptance of the suggestion topresent the supplemental content, or both.

In operation 738, as shown in FIG. 7-8, the synchronization module 232receives an acceptance of the suggestion. For example, as shown in FIG.8, operation 738 may include operation 832, in which the synchronizationmodule 232 receives the acceptance from a remote control (e.g., remotecontrol device) that is configured to fully or partially control themedia device 140. The acceptance may be received by detecting that abutton or key on a remote control for the media device 140 has beenpressed to indicate that the suggestion is accepted (e.g., to indicatethat the supplemental content is to be presented). As another example,as shown in FIG. 8, operation 738 may include operation 833, in whichthe synchronization module 232 receives the acceptance of the suggestionfrom the companion device 130. This may be performed by detecting that abutton or key (e.g., physical or virtual) on the companion device 130has been pressed to indicate that the suggestion is accepted.

As shown in FIG. 9, the method 700 may include one or more of operations505, 905, 906, 910, 935, and 936. As noted above, operation 505 involvesthe detection module 330 of the media device 140 detecting the companiondevice 130 (e.g., coming within IR range, wireless networking range, orwithin a predetermined threshold distance of the media device 140).

In operation 905, the detection module 330 of the media device 140determines that the detected companion device 130 is on a trusted list(e.g., a list of trusted companion devices, among which is the companiondevice 130), which may have the effect of providing a degree of securitychecking that only trusted companion devices may be used. Thisdetermination may be performed based on (e.g., in response to) thedetection of the companion device 130 in operation 505. The trusted listmay be included (e.g., stored) in the detection module 330, included inthe synchronization module 232 (e.g., as generated by the server module230 of the media server machine 110), or provided to the detectionmodule 330 or the synchronization module 232 (e.g., as an update) by themedia server machine 110, by the database 115, or by the web servermachine 120 (e.g., via SSL communication).

In operation 906, the detection module 330 of the media device 140establishes a communication link with the companion device 130 (e.g.,with its companion module 234). This communication link may beestablished based on the companion device 130 being brought within IRrange, within wireless networking range, within a predeterminedthreshold distance of the media device 140, or any suitable combinationthereof. In addition, this communication link may be established basedon the determination in operation 905 that the detected companion device130 is on the trusted list. Examples of such a communication linkinclude an IR connection, wireless networking connection (e.g., personalarea network (PAN) connection, such as a Bluetooth connection), or anysuitable combination thereof.

In operation 910, the detection module 330 of the media device 140detects one or more additional companion devices (e.g., companion device150). Such detection of multiple companion devices (e.g., companiondevices 130 and 150) enables the media device 140 to perform operation935, in which the presentation module 320 of the media device 140presents a menu of detected companion devices (e.g., companion devices130 and 150) on the display 142. The menu may indicate that the detectedcompanion devices are available to present the supplemental content. Thepresented menu, in some example embodiments, may be limited to onlythose detected companion devices that are identified on the trusted listof companion devices. The presented menu may enable one or more users(e.g., user 132 or user 152) to select which of the detected companiondevices should be used to present the supplemental content. In certainexample embodiments, the selection may be made from the presented menu(e.g., by the user 132 navigating presented menu and making theselection using a remote control for the media device 140). In someexample embodiments, the selection may be made from one or more of thedetected companion devices (e.g., by the user 132 pressing a button orkey (e.g., physical or virtual) on the companion device 130 to selectthe companion device 130). In such example embodiments, operation 935may be omitted.

In operation 936, the synchronization module 232 of the media device 140receives a selection that indicates which companion device (e.g.,companion device 130) from the presented menu is selected for presentingthe supplemental content. For example, the selection may be received bydetecting that one or more buttons or keys (e.g., a navigation up key,navigation down key, or a selection confirmation key) on a remotecontrol for the media device 140 has been pressed indicate theselection. As another example, the selection may be performed bydetecting that a button or key (e.g., physical or virtual) on thecompanion device 130 has been pressed to indicate the selection.

In example embodiments that include operations 935 and 936, the sendingof the launch instruction in operation 540 may be performed based on(e.g., in response to) the selection received in operation 936. Forexample, the selection may identify the companion device 130 as beingselected for presentation of the supplemental content, and the launchinstruction may be sent in operation 540 to the companion device 130 inaccordance with the received selection.

FIG. 10 is a flowchart illustrating operations of the companion device130 in performing a method 1000 of synchronizing the application 440,according to some example embodiments. Operations and the method 1000may be performed using modules described above with respect to FIG. 4.As shown in FIG. 10, the method 1000 includes operations 541 and 550,and may include one or more of operations 941, 1031, 1032, 1033, 1041,1042, 1051, and 1052.

In operation 941, the access module 410 of the companion device 130receives the application 440 from the media device 140 (e.g., as aresult of the media device 140 in performing operation 734). The accessmodule 410 may then store the application 440 on the companion device130 (e.g., in memory). According to various example embodiments,operation 941 may be performed before, during, or after operation 541.

In operation 1031, the companion module 234 of the companion device 130receives a prompt to present the suggestion discussed above with respectto operation 831. The prompt may be sent from the synchronization module232 of the media device 140. In some example embodiments, the companionmodule 234 receives the prompt via the access module 410 of thecompanion device 130.

In operation 1032, the companion module 234 presents the suggestion onthe screen 450. For example, the companion module 234 may causepresentation module 420 to present the suggestion on the screen 450. Asnoted above, the suggestion may be or include a single icon thatidentifies a button or key that, if pressed, would indicate that thesupplemental content is to be presented by the application 440. Anacceptance of the presented suggestion may be received by the screen 450(e.g., as a touch input from the user 132 on the identified button orkey).

In operation 1033, the companion module 234 of the companion device 130submits the acceptance of the suggestion to the media device 140 (e.g.,via its synchronization module 232). This may enable the media device140 to provide the launch instruction in operation 540 based on (e.g.,in response to) the acceptance of the suggestion. As noted above, inoperation 541, the access module 410 of the companion device 130receives the launch instruction from the media device 140.

In certain example embodiments, the presentation of the suggestion andthe detection of the acceptance is handled completely by the companiondevice 130. In such example embodiments, operations 1041 and 1042 may beperformed after the launch instruction is received in operation 541. Inoperation 1041, the companion module 234 presents the suggestion on thescreen 450 (e.g., by causing the presentation module 420 to present thesuggestion on the screen 450). Operation 1041 may be performed based on(e.g., in response to) the launch instruction being received inoperation 541. In operation 1042, an acceptance of the presentedsuggestion is received by the screen 450 (e.g., as a touch input fromthe user 132). In example embodiments that include operation 1042, thelaunching of the application 440 in operation 550 may be performed basedon the detected acceptance of the suggestion.

One or more of operations 1051 and 1052 may be performed as part ofoperation 550, in which the companion module 234 of the companion device130 launches the application 440 on the companion device 130. Inoperation 1051, the companion module 234 causes the application 440 toobtain and store the supplemental content (e.g., as identified in thereceived launch instruction) on the companion device 130. For example,the companion module 234 may cause the application 440 to obtain thesupplemental content from the web server machine 120 and then store thesupplemental content in a memory (e.g., a browser cache) of thecompanion device 130. This may enable the application 440 to besubsequently launched multiple times to present the supplementalcontent.

In operation 1052, the companion module 234 causes the application 440to initiate a presentation of the supplemental content on the screen 450of the companion device 130. For example, the application 440 mayinitiate the presentation within a browser window of the application440, where the browser window is rendered to the screen 450.Accordingly, since the application 440 was launched based on thereceived launch instruction, which was sent based on the app-syncindicator being received contemporaneously with the media content, thescreen 450 may launch the application 440 synchronously with the mediacontent being presented on the display 142. Moreover, the screen 450 mayimmediately display the supplemental content contemporaneously with thepresentation of the media content (e.g., while the media content ispresented on the display 142).

FIG. 11 is a block diagram illustrating relationships among mediacontent 1110 and 1120, app-sync indicators 1112 and 1122, andsupplemental content 1115 and 1125, within a datastream 1100, accordingto some example embodiments. The datastream 1100 may be a programstream, a transport stream, or any other suitable data feed thatmultiplexes various media content with various app sync indicators. Asshown in FIG. 11, the media content 1110 may be a first clip, scene, orprogram within the datastream 1100, and the media content 1110 may beprovided contemporaneously with the app-sync indicator 1112 in thedatastream 1100. Similarly, the media content 1120 may be a second clip,scene, or program within the datastream 1100, and the media content 1120may be provided contemporaneously with the app-sync indicator 1122 inthe datastream 1100. Hence, the app-sync indicator 1112 may correspondto the media content 1110, and the app-sync indicator 1122 maycorrespond to the media content 1120.

Furthermore, the app-sync indicator 1112 may correspond to thesupplemental content 1115. As indicated in FIG. 11, the supplementalcontent 1115 may be or include a webpage or streaming video, and thesupplemental content 1115 may be distinct from the media content 1110,but still pertinent to the media content 1110. Likewise, thesupplemental content 1125 may be or include a webpage or streamingvideo, and the supplemental content 1125 may be distinct from the mediacontent 1120, but nonetheless pertinent to the media content 1120.

The correspondence relationship between the app-sync indicator 1112 andthe media content 1110 may arise based on the app-sync indicator 1112being provided contemporaneously with the media content 1110 within thedatastream 1100. For example, the contemporaneous provision of the mediacontent 1110 and the app-sync indicator 1112 may be within a short timeperiod (e.g., as perceived by the user 132), such as within five secondsof each other. A similar correspondence relationship may exist betweenthe app-sync indicator 1122 and the media content 1120.

The correspondence relationship between the app-sync indicator 1112 andthe supplemental content 1115 may arise based on the app-sync indicator1112 being or including an identifier of the supplemental content 1115(e.g., URI), a reference to the supplemental content 1115 (e.g., a URL),or any suitable combination thereof. A similar correspondencerelationship may exist between the app-sync indicator 1122 and thesupplemental content 1125.

In certain example embodiments, the full functionality of app-syncindicator 1112 may be implemented by multiple app-sync indicators thateach perform just a portion of this full functionality. For example, afirst app-sync indicator may identify the synchronization module 232 ofthe media device 140, and the media device 140 may launch itssynchronization module 232 based on (e.g., response to) this firstapp-sync indicator being provided in the datastream (e.g., providedcontemporaneously with the media content 110, in a manner similar tothat described above for the app-sync indicator 1112). This firstapp-sync indicator may contain no information that identifies theapplication 440 to be launched by the companion device 130, and thisfirst app-sync may contain no information that identifies anysupplemental content (e.g., supplemental content 1115) to be presentedby the application 440. In such a situation, a second app-sync indicatormay be provided in the datastream 1100 (e.g., contemporaneously with themedia content 1110). As an example, this second app-sync indicator mayidentify the application 440, as well as the supplemental content 1115to be presented by the application 440. As another example, thesynchronization module 232 may have or obtain an identifier of theapplication 440 (e.g., as stored data, hard-coded data, or data accessedfrom the database 115, the media server machine 110, or the web servermachine 120), and the second-sync indicator may identify only thesupplemental content 1115.

According to various example embodiments, one or more of themethodologies described herein may facilitate synchronizing thelaunching of an application on a companion device. Moreover, one or moreof the methodologies described herein may enable synchronization of suchan application launch with the media content being presented on adisplay. Furthermore, one or more the methodologies described herein mayfacilitate retrieval and presentation of supplemental content via thesynchronized application, so that the supplemental content is presentedcontemporaneously with the media content, as the media content ispresented on the display.

When these effects are considered in aggregate, one or more of themethodologies described herein may obviate a need for certain efforts orresources that otherwise would be involved in synchronizing thelaunching of an application with media content, contemporaneous displayof supplemental content with media content, or any suitable combinationthereof. Efforts expended by a user in identifying, launching, orsynchronizing the display of supplemental content on a companion devicewhile media content is being presented by a media device may be reducedby one or more of the methodologies described herein. Computingresources used by one or more machines, databases, or devices (e.g.,within the network environment 100) may similarly be reduced. Examplesof such computing resources include processor cycles, network traffic,memory usage, data storage capacity, power consumption, and coolingcapacity.

As an example of a use case, the media server machine 110 may embed theapp-sync indicator 1112 in an AIT within the datastream 1100, which mayinclude a broadcast audio-video stream of a live baseball game as themedia content 1110, and this AIT may reference a webpage (e.g., byincluding a URL to be opened via a browser) as the supplemental content1115. The media device 140 receives the AIT contemporaneously withaudio-video content that depicts a particular point or event in thebaseball game (e.g., such as particular player becoming the current “atbat” player). In response to the AIT, the media device 140 may display agreen button on the display 142 for 30 seconds, after which the buttonfades away. The green button may be a single icon and may correspond toa green key on a remote control that is operable by the user 132 tofully or partially control the media device 140 and thereby control whatis shown on the display 142.

On the media device 140, if the green key on the remote control isactivated during the 30 second period, the synchronization module 232may request from the detection module 330 a list of nearby companiondevices (e.g., companion devices 130 and 150). In some exampleembodiments, the green key may be activated after the 30 second period(e.g., if the media device 140 registered a listener for the green key,and this listener is still active). The detection module 330 may detectthose companion devices that are within a threshold distance andconfigured with the companion module 234. Such companion devices (e.g.,companion devices 130 and 150) may be identified in a list (e.g., amenu) provided by the detection module 330 to the synchronization module232. The synchronization module 232 may then display the list on thedisplay 142, which may allow the user 132 to navigate the list (e.g., bypressing one or more arrow keys on the remote control) and select whichof the listed companion devices (e.g., companion device 130) should beused to launch and execute a synchronized application (e.g., application440). In response to a selection being made, the synchronization module232 sends the launch instruction to the selected one or more companiondevices (e.g., companion device 130). In some example embodiments, nolist of detected companion devices is shown on the display 142, and oneor more detected companion devices (e.g., identified on a trusted listof companion devices) may be automatically selected for launchingexecuting a synchronized application (e.g., application 440).

The launch instruction may include the URL of the webpage, which maycontain supplemental content that is related to the live baseball game.Such a webpage may include one or more links to supplemental contentpresentable by the application 440 (e.g., supplemental content 1115).Examples of such supplemental content include statistics for each teaminvolved in the baseball game, options to select alternate camera anglesthat depict the live baseball game from different angles, and an optionto select an alternate audio feed for the live baseball game (e.g., aradio broadcaster's announcements that describe the live baseball gameplay-by-play, which announcements may be more informative than the mediacontent of the live baseball game). The user 132 may independentlyselect his chosen option for his companion device 130, without affectingwhat is shown by the media device 140 on the display 142, and withoutaffecting what the user 152 may select for presentation on her companiondevice 150.

Moreover, the live baseball game may depict a current “at bat” player,and the webpage may offer supplemental content that refers to the sameplayer (e.g., supplemental content 1115). For example, the AIT maycontain a reference to the player (e.g., by name); the launchinstruction may include the reference to the player; and the application440 may be launched with the reference to the player as input (e.g., asan input parameter for starting the application 440). The reference maybe updated when the current “at bat” player changes (e.g., within a newversion of the same AIT or in a new AIT embedded in the datastream).Accordingly, the media server machine can embed such references into thedatastream as events that dynamically indicate changes to thesupplemental content for the live baseball game (e.g., a change thatreplaces the supplemental content 1115 with the supplemental content1125). Any one or more of such events may be processed by thesynchronization module 232 of the media device 140. Furthermore,processing such an event may cause the synchronization module 232 totransmit additional synchronization signals (e.g., metadata similar toan AIT) to the companion module 234 on the device 130, to theapplication 440 (e.g., directly), or both.

As an example feature, according to various example embodiments, thesynchronization module 232 of the media device 140 may provide theapplication 440 on the companion device 130 with an instruction tochange the supplemental content in response to the user 132 changing thedatastream being accessed (e.g., receive) by the media device 140 (e.g.,by the user 132 changing broadcast channels to view a differentbroadcast datastream). For example, this instruction to change thesupplemental content may be or include a URL of new supplemental contentthat corresponds to the new datastream. In some example embodiments,this instruction may be provided to the companion module 234 on thecompanion device 130, and the companion module to a 34 may be configuredto provide this URL to the application 440 upon its next launch.Accordingly, if the application 440 closed, and the user 132 changeschannels on the media device 140, the application 440 may be launchedwith appropriate supplemental content that corresponds to the newchannel.

As another example feature, according to various example embodiments,detection of new companion devices may be dynamic and ongoing. Hence, afurther user (e.g., a newly arrived user, beyond users 132 and 152) maybring a further companion device (e.g., a newly arrived companiondevice, beyond companion devices 130 and 150) into physical proximity ofthe media device 140. The media device 140 may detect this new companiondevice and, in response, present the green button as discussed above.This may enable a convenient way to flexibly add additional users fordisplaying supplemental content. For example, if the media content is agame show, and the supplemental content is a webpage that lets the users132 and 152 play along on their respective companion devices 130 and150, one or more additional users may join the game by pressing thegreen key and selecting their own companion devices for presenting thewebpage.

As a further example feature, according to various example embodiments,the application 440 may be configured to store some or all of thesupplemental content (e.g., supplemental content 1112) presentable bythe application 440, store reference (e.g., a URL) to some or all of thesupplemental content, or any suitable combination thereof. This abilityto store one or more portions of the supplemental content, or referencesthereto, may enable the application 440 to present these portions in aflexible manner depending on network performance (e.g., data transferspeeds within the network 192). For example, a recipe from a cookingshow may be stored by the application 440 for repeated presentation at alater time (e.g., days or months after the presentation of cooking showhas ended). The application 440 may be configured to determine anexpected network performance (e.g., always well-connected, disconnectedon weekends, or any other pattern of network performance). Based on thisexpected network performance, the application 440 may determine whethera portion of the supplemental content is to be stored, or whether areference to the portion is to be stored. For example, if the networkperformance is expected to be high at a given time, but the actualnetwork performance is low, the application 440 may store a reference toportion of the supplemental content, so that the portion may be accessedat a later time when the actual network performance is high. As anotherexample, if the network performance is expected to be high, and theactual network performance is also high, the application 440 based storethe actual portion of the supplemental content (e.g., taking advantageof the high network performance). In some hybrid situations, theapplication 440 may initiate storage of both the portion of thesupplemental content and the reference to the supplemental content.Moreover, the application 440 may initiate storage of one portion of thesupplemental content (e.g., a recipe from the cooking show) and initiatestorage of a reference to another portion of the supplemental content(e.g., a video of that recipe being made).

In some example versions of this use case, the application 440 (e.g., abrowser) on the companion device 130 is configured to communicate withthe presentation module 320 on the media device 140. The presentationmodule 320 may include a browser or other suitable software that allowsthe application 440 on the companion device 130 to present some or allof the supplemental content on the display 142 of the media device 140.Accordingly, the user 132 may choose to activate a button labeled “sendsupplemental content to main screen,” and allow other users (e.g., user152) to experience the same supplemental content. Such activation maycause some or all of the supplemental content to be sent from thecompanion device 130 to the media device 140 for presentation on thedisplay 142. In some example embodiments, such activation causes areference (e.g., a URL) to some or all of the supplemental content to besent from the companion device 130 to the media device 140, and themedia device 140 may obtain (e.g., access) some or all of thesupplemental content for presentation on the display 142.

Where multiple companion devices (e.g., companion devices 130 and 150)are used, according to some example embodiments, the application to belaunched may vary from companion device to companion device. Forexample, the synchronization module 232 may have (e.g., stored) orobtain (e.g., access or receive) a profile for each individual companiondevice. Such profiles may form all or part of a trusted list ofcompanion devices. The profile for a given companion device (e.g.,companion device 130) may identify the application (e.g., application440) to be launched. In certain example embodiments, the profile for acompanion device (e.g., companion device 130) is or includes a profileof the primary user (e.g., user 132) of the companion device.

FIG. 12 is a block diagram illustrating components of a machine 1200,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium, acomputer-readable storage medium, or any suitable combination thereof)and perform any one or more of the methodologies discussed herein, inwhole or in part. Specifically, FIG. 12 shows a diagrammaticrepresentation of the machine 1200 in the example form of a computersystem and within which instructions 1224 (e.g., software, a program, anapplication, an applet, an app, or other executable code) for causingthe machine 1200 to perform any one or more of the methodologiesdiscussed herein may be executed, in whole or in part. In alternativeembodiments, the machine 1200 operates as a standalone device or may beconnected (e.g., networked) to other machines. In a networkeddeployment, the machine 1200 may operate in the capacity of a servermachine or a client machine in a server-client network environment, oras a peer machine in a distributed (e.g., peer-to-peer) networkenvironment. The machine 1200 may be a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a STB, a personal digital assistant (PDA), acellular telephone, a smartphone, a web appliance, a network router, anetwork switch, a network bridge, or any machine capable of executingthe instructions 1224, sequentially or otherwise, that specify actionsto be taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 1224 to perform all or part of any one or more of themethodologies discussed herein.

The machine 1200 includes a processor 1202 (e.g., a central processingunit (CPU), a graphics processing unit (GPU), a digital signal processor(DSP), an application specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), or any suitable combinationthereof), a main memory 1204, and a static memory 1206, which areconfigured to communicate with each other via a bus 1208. The machine1200 may further include a graphics display 1210 (e.g., a plasma displaypanel (PDP), a light emitting diode (LED) display, a liquid crystaldisplay (LCD), a projector, or a cathode ray tube (CRT)). The machine1200 may also include an alphanumeric input device 1212 (e.g., akeyboard), a cursor control device 1214 (e.g., a mouse, a touchpad, atrackball, a joystick, a motion sensor, or other pointing instrument), astorage unit 1216, a signal generation device 1218 (e.g., a speaker),and a network interface device 1220.

The storage unit 1216 includes a machine-readable medium 1222 on whichare stored the instructions 1224 embodying any one or more of themethodologies or functions described herein. The instructions 1224 mayalso reside, completely or at least partially, within the main memory1204, within the processor 1202 (e.g., within the processor's cachememory), or both, during execution thereof by the machine 1200.Accordingly, the main memory 1204 and the processor 1202 may beconsidered as machine-readable media. The instructions 1224 may betransmitted or received over a network 1226 (e.g., network 190 ornetwork 192) via the network interface device 1220.

As used herein, the term “memory” refers to a machine-readable mediumable to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 1222 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions. The term “machine-readable medium” shall also be taken toinclude any medium, or combination of multiple media, that is capable ofstoring instructions for execution by a machine (e.g., machine 1200),such that the instructions, when executed by one or more processors ofthe machine (e.g., processor 1202), cause the machine to perform any oneor more of the methodologies described herein. Accordingly, a“machine-readable medium” refers to a single storage apparatus ordevice, as well as “cloud-based” storage systems or storage networksthat include multiple storage apparatus or devices. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, one or more tangible data repositories in the form of asolid-state memory, an optical medium, a magnetic medium, or anysuitable combination thereof.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A “hardware module” is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware modules of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as a fieldprogrammable gate array (FPGA) or an ASIC. A hardware module may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwaremodule may include software encompassed within a general-purposeprocessor or other programmable processor. It will be appreciated thatthe decision to implement a hardware module mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Software mayaccordingly configure a processor, for example, to constitute aparticular hardware module at one instance of time and to constitute adifferent hardware module at a different instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, a processor being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented modules. Moreover, theone or more processors may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anapplication program interface (API)).

The performance of certain operations may be distributed among the oneor more processors, not only residing within a single machine, butdeployed across a number of machines. In some example embodiments, theone or more processors or processor-implemented modules may be locatedin a single geographic location (e.g., within a home environment, anoffice environment, or a server farm). In other example embodiments, theone or more processors or processor-implemented modules may bedistributed across a number of geographic locations.

Some portions of the subject matter discussed herein may be presented interms of algorithms or symbolic representations of operations on datastored as bits or binary digital signals within a machine memory (e.g.,a computer memory). Such algorithms or symbolic representations areexamples of techniques used by those of ordinary skill in the dataprocessing arts to convey the substance of their work to others skilledin the art. As used herein, an “algorithm” is a self-consistent sequenceof operations or similar processing leading to a desired result. In thiscontext, algorithms and operations involve physical manipulation ofphysical quantities. Typically, but not necessarily, such quantities maytake the form of electrical, magnetic, or optical signals capable ofbeing stored, accessed, transferred, combined, compared, or otherwisemanipulated by a machine. It is convenient at times, principally forreasons of common usage, to refer to such signals using words such as“data,” “content,” “bits,” “values,” “elements.” “symbols,”“characters,” “terms,” “numbers,” “numerals,” or the like. These words,however, are merely convenient labels and are to be associated withappropriate physical quantities.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or any suitable combination thereof), registers, orother machine components that receive, store, transmit, or displayinformation. Furthermore, unless specifically stated otherwise, theterms “a” or “an” are herein used, as is common in patent documents, toinclude one or more than one instance. Finally, as used herein, theconjunction “or” refers to a non-exclusive “or,” unless specificallystated otherwise.

The following enumerated descriptions define various example embodimentsof methods, machine-readable media, and systems (e.g., apparatus)discussed herein:

In a first example embodiment, a media device is further defined byincluding the following additional features:

the app-sync indicator includes a URL that locates supplemental contentthat corresponds to the media content;

the synchronization module configures the processor to extract the URLfrom the app-sync indicator;

the launch instruction includes the URL extracted from the app-syncindicator; and

the companion device launches the application with the URL as an inputto the application.

In a second example embodiment, the media device of the precedingdescription is further defined by including the following additionalfeature:

the synchronization module configures the processor to determine, priorto sending the launch instruction to the companion device, that the URLis referenced by a list of trusted URLs.

In a third example embodiment, the media device of any of the abovedescriptions is further defined by including the following additionalfeatures:

the app-sync indicator and the launch instruction identify theapplication among multiple applications stored by the companion device;

the synchronization module configures the processor to send the launchinstruction based on the app-sync indicator identifying the application;and

the companion device launches the application based on the launchinstruction identifying the application.

In a fourth example embodiment, the media device of the precedingdescription is further defined by including the following additionalfeature:

the synchronization module configures the processor to determine, priorto sending the launch instruction to the companion device, that theapplication is referenced by a list of trusted applications.

In a fifth example embodiment, the media device of any of the abovedescriptions is further defined by including the following additionalfeatures:

the app-sync indicator includes a reference to supplemental content forthe media content;

the synchronization module configures the processor to extract thereference to the supplemental content from the app-sync indicator;

the launch instruction includes the reference to the supplementalcontent; and

the companion device, in launching the application, causes theapplication to obtain and store the supplemental content on thecompanion device.

In a sixth example embodiment, the media device of any of the abovedescriptions is further defined by including the following additionalfeatures:

the app-sync indicator includes a reference to supplemental content forthe media content; and

the synchronization module configures the processor to extract thereference to the supplemental content from the app-sync indicator;

the launch instruction includes the reference to the supplementalcontent; and

the companion device, in launching the application, causes theapplication to initiate a presentation of the supplemental content on ascreen of the companion device.

In a seventh example embodiment, the media device of the precedingdescription is further defined by including the following additionalfeatures:

the reception module is configured to receive a datastream via a firstnetwork; and

the synchronization module configures the processor to provide thesupplemental content to the companion device via a second network.

In an eighth example embodiment, the media device of the sixth orseventh embodiments is further defined by including the followingadditional features:

the media content depicts an event from a first camera angle; and

the supplemental content depicts the event from a second camera angle.

In a ninth example embodiment, the media device of any of the sixth,seventh, or eighth embodiments is further defined by including thefollowing additional feature:

the synchronization module configures the processor to present, prior tosending the launch instruction to the companion device, a suggestionthat the companion device present the supplemental content.

In a tenth example embodiment, the media device of the precedingdescription is further defined by including the following additionalfeature:

the synchronization module configures the processor to present thesuggestion on the display and receives an acceptance of the suggestionfrom a remote control configured to control the media device.

In an eleventh example embodiment, the media device of the ninthembodiment is further defined by including the following additionalfeature:

the synchronization module configures the processor to present thesuggestion by causing the companion device to present the suggestion ona screen of the companion device.

In a twelfth example embodiment, the media device of the precedingdescription is further defined by including the following additionalfeature:

the synchronization module configures the processor to receive anacceptance of the suggestion from the companion device.

In a thirteenth example embodiment, the media device of any of the abovedescriptions is further defined by including the following additionalfeature:

the suggestion is a single icon that indicates an availability of thesupplemental content for presentation and identifies a button that isoperable to submit the acceptance of the suggestion.

In a fourteenth example embodiment, the media device of any of the abovedescriptions is further defined by including the following additionalfeature:

a detection module configured to present, prior to the sending of thelaunch instruction to the companion device, a menu of detected companiondevices on the display and receive a selection that indicates thecompanion device is selected from the presented menu.

In a fifteenth example embodiment, the media device of any of the abovedescriptions is further defined by including the following additionalfeature:

the detection module is configured to establish, prior to sending thelaunch instruction to the companion device, a communication link withthe companion device based on the companion device being brought withina threshold distance of the media device.

In a sixteenth example embodiment, the media device of the precedingdescription is further defined by including the following additionalfeature:

the detection module is configured to determine, prior to establishingthe communication link with the companion device, that the companiondevice is referenced by a list of trusted companion devices.

In a seventeenth example embodiment, the media device of any of abovedescriptions is further defined by including the following additionalfeature:

the media device is inadequate to execute the application.

In an eighteenth example embodiment, the companion device includes thefollowing components:

an access module configured to receive a launch instruction sent basedon an app-sync indicator provided contemporaneously with media contentwithin a datastream received by a media device that sent the launchinstruction; and

a processor configured by a companion module to launch an application inresponse to the launch instruction sent from the media device based onthe app-sync indicator provided contemporaneously with the media contentwithin the datastream received by the media device.

In a nineteenth example embodiment, the companion device of thepreceding description is further defined by including the followingadditional feature:

the access module is configured to receive the application from themedia device prior to the launching of the application in response thelaunch instruction sent from the media device.

In a twentieth example embodiment, the companion device of theeighteenth or nineteenth embodiment is further defined by including thefollowing additional features:

the app-sync indicator includes a URL that locates supplemental contentthat corresponds to the media content;

the media device is configured to extract the URL from the app-syncindicator;

the launch instruction includes the URL extracted from the app-syncindicator; and

the companion module configures the processor to launch the applicationwith the URL as an input to the application.

In a twenty-first example embodiment, the companion device of any of theeighteenth, nineteenth, or twentieth embodiments is further defined byincluding the following additional features:

the app-sync indicator and the launch instruction identify theapplication among multiple applications stored by the companion device;

the media device sent the launch instruction based on the app-syncindicator identifying the application; and

the companion device launches the application based on the launchinstruction identifying the application.

In a twenty-second example embodiment, the companion device of any ofthe above companion device descriptions is further defined by includingthe following additional features:

the app-sync indicator includes a reference to supplemental content forthe media content;

the media device is configured to extract the reference to thesupplemental content from the app-sync indicator;

the launch instruction includes the reference to the supplementalcontent; and

the companion module configures the processor, in launching theapplication, to cause the application to obtain and store thesupplemental content on the companion device.

In a twenty-third example embodiment, the companion device of any of theabove companion device descriptions is further defined by including thefollowing additional features:

the app-sync indicator includes a reference to supplemental content forthe media content;

the media device is configured to extract the reference to thesupplemental content from the app-sync indicator;

the launch instruction includes the reference to the supplementalcontent; and

the companion module configures the processor, in launching theapplication, to cause the application to initiate a presentation of thesupplemental content on a screen of the companion device.

In a twenty-fourth example embodiment, the companion device of thepreceding description is further defined by including the followingadditional features:

a network-based media system provides the datastream to the media devicevia a first network; and

the access module is configured to receive the supplemental content viaa second network.

In a twenty-fifth example embodiment, the companion device of thetwenty-third or twenty-fourth embodiment is further defined by includingthe following additional features:

the media content depicts an event from a first camera angle; and

the supplemental content depicts the event from a second camera angle.

In a twenty-sixth example embodiment, the companion device of any of theabove companion device descriptions is further defined by including thefollowing additional feature:

the companion module configures the processor to present a suggestion ona screen of the companion device that the supplemental content be shownon the screen.

In a twenty-seventh example embodiment, the companion device of thepreceding description is further defined by including the followingadditional feature:

the companion module configures the processor to detect an acceptance ofthe suggestion presented on the screen.

In a twenty-eighth example embodiment, the companion device of any ofthe above companion device descriptions is further defined by includingthe following additional feature:

a detection module configured to present, prior to the receiving of thelaunch instruction, a menu of detected companion devices on a screen ofthe companion device, the companion device being listed in the menu.

In a twenty-ninth example embodiment, the companion device of thepreceding description is further defined by including the followingadditional feature:

the detection module is configured to receive a selection that indicatesthe companion device is selected from the presented menu.

In a thirtieth example embodiment, the companion device of thetwenty-eighth or twenty-ninth embodiment is further defined by includingthe following additional feature:

the detection module is configured to establish a communication linkwith the media device based on the media device being brought within athreshold distance of the companion device.

In a thirty-first example embodiment, the companion device of thepreceding description is further defined by including the followingadditional feature:

the detection module, prior to establishing the communication link withthe media device, determines that the media device is referenced by alist of trusted media devices.

In a thirty-second example embodiment, the companion device of any ofthe above companion device descriptions is further defined by includingthe following additional feature:

the media device is inadequate to execute the application.

In a thirty-third example embodiment, a media device includes thefollowing components:

a reception module configured to access a datastream that includes mediacontent and an app-sync indicator associated with the media content;

a presentation module configured to cause presentation (e.g., display)of the media content on a display (e.g., display device);

detection module configured to detect a companion device in physicalproximity to the media device (e.g., to the detection module); and

a processor configured by a synchronization module to send, to thecompanion device, a launch instruction to cause launching of anapplication corresponding to the app-sync indicator on the companiondevice, the launch instruction being sent contemporaneously with thepresentation (e.g., display) of the media content on the display (e.g.,display device).

What is claimed is:
 1. A method comprising: accessing, by one or moreprocessors, an app-sync indicator associated with an application amongmultiple applications configured to run on a companion device, theapp-sync indicator being associated with media content; generating, bythe one or more processors, a datastream that includes the media contentand the app-sync indicator; and communicating, by the one or moreprocessors, the datastream to a media device configured to performoperations that comprise: causing presentation of the media content on adisplay communicatively coupled to the media device; detecting thecompanion device; and providing a trigger to the companion device inresponse to identifying the appsync indicator in the datastream to causethe companion device to run the application associated with the app-syncindicator.
 2. The method of claim 1, wherein: the app-sync indicatorassociated with the application identifies the application among themultiple applications; the trigger provided by the media device to thecompanion device identifies the application among the multipleapplications; and the provided trigger causes the companion device torun the application that is identified by the trigger and identified bythe app-sync indicator.
 3. The method of claim 1, wherein: thegenerating of the datastream includes inserting an applicationidentifier that identifies the application into the app-sync indicator;and the app-sync indicator with the inserted application identifieridentifies the application among the multiple applications.
 4. Themethod of claim 1, wherein: the generating of the datastream includesinserting the application into the datastream prior to the media contentand the app-sync indicator within the datastream; and the companiondevice receives the application via the datastream prior to the providedtrigger causing the companion device to run the application.
 5. Themethod of claim 1, wherein: the media device is configured to verifythat the application is referenced by a list of trusted applicationsprior to providing the trigger to the companion device.
 6. The method ofclaim 1, wherein: the app-sync indicator includes a uniform resourcelocator (URL) that locates supplemental content associated with themedia content; the media device is configured to extract the URL fromthe app-sync indicator; and the trigger provided by the media deviceincludes the URL extracted from the app-sync indicator and causes thecompanion device to run the application with the URI, as an input to theapplication.
 7. The method of claim 6, wherein: the media device isconfigured to verify that the URI is referenced by a list of trustedURLs prior to providing the trigger to the companion device.
 8. Themethod of claim 1, wherein: the app-sync indicator includes a referenceto supplemental content associated with the media content; the mediadevice is configured to extract the reference from the app-syncindicator; and the trigger provided by the media device includes thereference to the supplemental content and causes the companion device toinitiate a presentation of the supplemental content by the companiondevice.
 9. The method of claim 8, wherein: the media content depicts anevent from a first camera angle; and the supplemental content depictsthe event from a second camera angle.
 10. The method of claim 8,wherein: the media device is configured to cause presentation of asuggestion prior to providing the trigger to the companion device tosuggest that the companion device present the supplemental content. 11.The method of claim 10, wherein: the media device is configured topresent the suggestion on a display of the media device and detect anacceptance of the suggestion from a remote control associated with themedia device.
 12. The method of claim 10, wherein: the media device isconfigured to cause the companion device to present the suggestion anddetect acceptance of the suggestion from the companion device.
 13. Themethod of claim 10, wherein: the suggestion includes a graphical iconthat indicates availability of supplemental content and identifies aremote control button operable to indicate acceptance of the suggestion.14. The method of claim 1, wherein: the media device is configured to,prior to providing the trigger to the companion device, present a menuof detected companion devices on a display of the media device anddetect an input that indicates the companion device has been selectedfrom the presented menu.
 15. The method of claim 1, wherein: the mediadevice is configured to, prior to providing the trigger to the companiondevice, verify that the companion device is referenced by a list oftrusted companion devices and, based on the companion device beingreferenced by the list of trusted companion devices, establish acommunication link with the companion device in response to thecompanion device being brought within a threshold distance of the mediadevice.
 16. The method of claim 1, wherein: the media device isinadequate to execute the application configured to run on the companiondevice.
 17. A non-transitory machine-readable storage medium comprisinginstructions that, when executed by one or more processors of a machine,cause the machine to perform operations comprising: accessing anapp-sync indicator associated with an application among multipleapplications configured to run on a companion device, the app-syncindicator being associated with media content; generating a datastreamthat includes the media content and the app-sync indicator; andcommunicating the datastream to a media device configured to performoperations that comprise: causing presentation of the media content on adisplay communicatively coupled to the media device; detecting thecompanion device; and providing a trigger to the companion device inresponse to identifying the appsync indicator in the datastream to causethe companion device to run the application associated with the app-syncindicator.
 18. The non-transitory machine-readable storage medium ofclaim 17, wherein: the app-sync indicator associated with theapplication identifies the application among the multiple applications;the trigger provided by the media device to the companion deviceidentifies the application among the multiple applications; and theprovided trigger causes the companion device to run the application thatis identified by the trigger and identified by the app-sync indicator.19. A system comprising: one or more processors; and a memory storinginstructions that, when executed by the one or more processors, causethe one or more processors to perform operations comprising: accessingan app-sync indicator associated with an application among multipleapplications configured to run on a companion device, the app-syncindicator being associated with media content; generating a datastreamthat includes the media content and the app-sync indicator; andcommunicating the datastream to a media device configured to performoperations that comprise: causing presentation of the media content on adisplay communicatively coupled to the media device; detecting thecompanion device; and providing a trigger to the companion device inresponse to identifying the appsync indicator in the datastream to causethe companion device to run the application associated with the app-syncindicator.
 20. The system of claim 19, wherein: the generating of thedatastream includes inserting an application identifier that identifiesthe application into the app-sync indicator; and the app-sync indicatorwith the inserted application identifier identifies the applicationamong the multiple applications.
 21. A media device comprising: one ormore processors; and a memory storing instructions that, when executedby the one or more processors, cause the one or more processors toperform operations comprising: receiving a datastream that includesmedia content and includes an app-sync indicator that is associated withthe media content and associated with an application among multipleapplications configured to run on a companion device; causingpresentation of the media content on a display communicatively coupledto the media device; detecting the companion device; and providing atrigger to the companion device in response to identifying the app-syncindicator in the datastream to cause the companion device to run theapplication associated with the app-sync indicator.
 22. A companiondevice comprising: one or more processors; and a memory storinginstructions that, when executed by the one or more processors, causethe one or more processors to perform operations comprising: storingmultiple applications on the companion device; detecting a media device;receiving a trigger from the media device in response to the mediadevice identifying an app-sync indicator in a received datastream thatincludes media content associated with the app-sync indicator, thetrigger indicating that an application among the multiple applicationsis associated with the app-sync indicator and requested to be run on thecompanion device; and in response to the trigger received from the mediadevice, running the application associated with the app-sync indicatoron the companion device.